Summary

• Register MCP server in KiloCode's global MCP configuration during install
• Remove MCP server entry from KiloCode config during uninstall
• Uses KiloCode MCP config format with mcpServers key and command path

KiloCode stores MCP configuration in:

~/.config/Code/User/globalStorage/kilocode.kilo-code/settings/mcp_settings.json

This PR automatically adds the codebase-memory-mcp server entry during install and removes it during uninstall.

Changes

• install.go

  • Added kilocodeConfigPath()
  • Added installKiloCodeMCP()
  • Added removeKiloCodeMCP()
  • Integrated with existing install/uninstall flow following the same pattern used for other MCP clients.

• install_test.go

  • Added tests for:

    • Config path generation
    • MCP server installation
    • Preservation of existing settings
    • Clean uninstall

Test Plan

• ✅ TestKiloCodeConfigPath — verifies correct config path resolution
• ✅ TestKiloCodeMCPInstall — creates config and registers MCP server
• ✅ TestKiloCodeMCPPreservesSettings — ensures existing settings are preserved
• ✅ TestKiloCodeMCPUninstall — verifies MCP entry removal

All existing tests pass:

go test ./cmd/codebase-memory-mcp -count=1

Screenshots -- provided below

KiloCode MCP configuration example after install:

{
  "mcpServers": {
    "codebase-memory-mcp": {
      "command": "/path/to/codebase-memory-mcp"
    }
  }
}

KiloCode MCP settings UI showing registered server.

Notes

This follows the same client integration pattern used for other MCP clients in the repository.

Adding KiloCode support allows users who run KiloCode as their MCP client to automatically install and manage the codebase-memory-mcp server using the existing CLI install/uninstall commands.